feat(providers): add Gemini 3.6 Flash and 3.5 Flash-Lite#5812
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
PR SummaryLow Risk Overview
No provider routing or API code changes—new IDs are picked up via existing Reviewed by Cursor Bugbot for commit 994d334. Configure here. |
Greptile SummaryThis PR expands the Google model registry with two Gemini Flash models.
Confidence Score: 5/5This looks safe to merge.
Important Files Changed
Reviews (2): Last reviewed commit: "feat(providers): add Gemini 3.6 Flash an..." | Re-trigger Greptile |
|
@greptile the one flagged thread was a false positive — the temperature/thinking support lists are derived at module load from each model entry's |
|
@cursor review |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 994d334. Configure here.
|
Verified both models against the live Gemini API (
Both models return HTTP 200 on |
Summary
gemini-3.6-flashto the Google provider registry (input $1.50/M, cached $0.15/M, output $7.50/M) and set it as the recommended Google flash modelgemini-3.5-flash-lite(input $0.30/M, cached $0.03/M, output $2.50/M), marked speed-optimizedrecommendedfromgemini-3.5-flashtogemini-3.6-flash(direct successor: better performance, 17% fewer output tokens)Type of Change
Testing
Tested manually —
bun run lintpasses; both models fall under thegoogleprovider so they're automatically hosted + billed.Checklist